|
|
|
|
|
|
|
Now run the client. Create a new project by choosing File|Create Project from the menu. You should see the Create Project dialog box, as illustrated in Figure 8.4. Enter Samsona Bank Teller System and click OK. Click on the new SourceSafe project and create a subproject (using the same steps) called Second Bank of Carrollton. This hierarchy is important in environments where an application might be reused for more than one in-house client/user group or commercial mass-market customer. |
|
|
|
|
|
|
|
|
Figure 8.4.
The Create Project dialog box. |
|
|
|
|
|
|
|
|
An object-oriented, iterative, and incremental development project requires a master SourceSafe project that is structured per increment, per iteration, with folders that reflect the various subsystems, components, use-case models, and documentation. For the Second Bank of Carrollton project folder, create subprojects named First Iteration, Second Iteration, Third Iteration, and Fourth Iteration. These correspond to the four use cases identified in Day 2: Open an Account, Close an Account, Deposit New Funds, and Withdraw Funds. |
|
|
|
|
|
|
|
|
Label each iteration by the name of the use case as well. To label each Iteration subproject, select the iteration project folder and choose File|Label from the menu. Figure 8.5 shows the Label dialog box with an entry for Open an Account. Each iteration, when complete, becomes an executable release, whether implemented as a standard executable or ActiveX component. |
|
|
|
|
|
|
|
|
Figure 8.5.
Creating a label for the First
Iteration. |
|
|
|
|
|
|
|
|
For each iteration, you need increments to help you move step by step to complete the iteration. Ideally, each increment is represented as a use-case scenario implemented in a sequence diagram. Thus, create an increment project per iteration, commenting each increment project according to the name of each sequence diagram in Table 2.2. Label |
|
|
|
|
|
